This repository has been archived by the owner on Mar 17, 2021. It is now read-only.
Add enum values of SW360 data model correctly #582
Merged
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
sschuberth
approved these changes
Sep 2, 2020
sschuberth
suggested changes
Sep 2, 2020
| @@ -64,8 +64,10 @@ In the following section there is an outline what data of SW360 ${docNameCap} ma | |||
| | Release Tag Url | This is a link to the OSS repos tag of the release used stored as external id with key `orig_repo`. | | |||
| | Software Heritage ID | A release ID in software heritage in the format "swh:1:rel:*", stored as external id with key `swh`. | | |||
| | Copyrights | Copyrights of the release, given in a String. Individual copyrights are separated by line. Stored in the additional data section with key `copyrights` | | |||
| | Change Status | An enumeration with values `changed` or `as-is` stored as additional data with key `change_status`. A changed component release should be stored as own release with an appendix to the original version, e.g. `1.2.3_modified_xyz`. Currently the implementation can only handle `as-is` components. | | |||
| | Change Status | An enumeration with values `CHANGED` or `AS_IS` stored as additional data with key `change_status`. A changed component release should be stored as own release with an appendix to the original version, e.g. `1.2.3_modified_xyz`. Currently the implementation can only handle `AS_IS` components. | | |||
There was a problem hiding this comment.
Commit message: Please make the reference to the issue go last (between body and footer) and use one of the auto-closing keywords.
| | Clearing Report | A file with curated data and the approval state. If the status of this attachment is `Accepted`, the Clearing State of the component release is `Approved`. Typically uploaded by compliance office tooling. | |
There was a problem hiding this comment.
Commit message: Please make the reference to the issue go last (between body and footer) and use one of the auto-closing keywords.
|
|
||
| **Note**: | ||
| All string fields in this data model have a limit of 2147483647 - 1 in length, since this is the frame size of the binary protocol used with thrift. |
neubs-bsi
force-pushed
the
neubs-bsi/doc/sw360_model_case_sensitiv
branch
2 times, most recently
from
222c0f4 to
3b79849
Compare
In the sw360 data model the documentation of the clearing states are now added and the enum values are case corrected to be upper case in the change status key. Relates to eclipse-archived#580. Signed-off-by: Stephanie Neubauer <[email protected]>
Closes eclipse-archived#580. Signed-off-by: Stephanie Neubauer <[email protected]>
neubs-bsi
force-pushed
the
neubs-bsi/doc/sw360_model_case_sensitiv
branch
from
3b79849 to
95521f2
Compare
|
Kudos, SonarCloud Quality Gate passed!
|
sschuberth
approved these changes
Sep 2, 2020
Sign up for free
to subscribe to this conversation on GitHub.
Already have an account?
Sign in.
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Issue: #580
In the sw360 data model the documentation of the clearing states
are now added and the enum values are case corrected to be
upper case in the change status key.
Request Reviewer
Type of Change
Type of change: documentation
How Has This Been Tested?
Checklist
Must:
Optional: (delete if not applicable)